chore: Reintroduce Python 3.11 support#3
Merged
Yolley merged 1 commit intoYolley:mainfrom Jan 28, 2026
Merged
Conversation
Owner
|
Hey, thank you for contribution, I'll merge the changes, but then also make some adjustments and make a release.
|
Author
|
It seems due to my lack of familiarity with the code changes that I underestimated the scope of changes. I'd like to apologize and reiterate my thanks for your time and help here! |
Owner
|
@nahua-aignx 2.3.0 is released with 3.11 support https://pypi.org/project/fastapi-cache2-fork/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello @Yolley, first of all thank you for forking and creating this package. My team is currently looking for a package that supports dynamic TTL calculation and distributed locking and
fastapi-cache2-forksatisfies these needs. Unfortunately, some of our services are still on py3.11.I took a quick look and the code changes to bring back py3.11 support should be minimal, e.g.
dec_hook[T] → dec_hookwhich uses the TypeVar that's still available in thecoder.pymodule. The rest I could found would just be config changes (pyproject.toml,tox.ini,CI matrix).May I ask if you'd be open to a PR to restore Python 3.11 support? Thanks in any case!